PART 1. TEXAS DEPARTMENT OF TRANSPORTATION
CHAPTER 9. CONTRACT AND GRANT MANAGEMENT
The Texas Department of Transportation (department) proposes the amendments to §§9.2, 9.15, 9.17, 9.23, and 9.24, relating to Contracts and Grant Management.
EXPLANATION OF PROPOSED AMENDMENTS
The purpose of this rulemaking is to clarify the rules of the Texas Transportation Commission (commission) concerning the requirements for submitting certain claims for contracts entered into and administered by the Texas Department of Transportation (department).
Amendments to §9.2, Contract Claim Procedure, in subsection (g)(2)(B), prohibit the use of any type of total cost method when making a claim for additional compensation. This prohibition ensures that claims for additional compensation are based on verifiable direct costs attributable to specific changes and impacts. Additional amendments allow the committee chair to waive the meeting requirement if the department does not dispute the contractor's claim because such a meeting is unnecessary and to specify that rescheduling of meetings is at the committee chair's discretion, which will prevent unnecessary delay. The term "chairman" is also replaced with "chair" to align with the language used in 43 TAC §1.1, Texas Transportation Commission. The amendments also correct the reference in subsection (a)(1)(C) to the title of Transportation Code, Chapter 223.
Amendments to §9.15, Acceptance of Bids, clarify in subsection (e) that the department evaluates only the apparent low bid to determine whether the bid is unbalanced and provide that the department may determine that the apparent low bid is nonresponsive if the evaluation shows that the apparent low bid is both mathematically and materially unbalanced. This change provides for efficiency in the selection of bids for awarding contracts.
Amendments to §9.17, Award of Contract, delete the requirement of subsection (a)(2) that the commission reject all bids for a project if the lowest bid is determined to be both mathematically and materially unbalanced. This requirement is unnecessary because under language added to §9.15, a determination that a low bid is mathematically and materially unbalanced may result in the bid being considered nonresponsive.
Amendments to §9.23, Evaluation and Monitoring of Contract Performance, clarify that an interim evaluation must be completed as needed and on each anniversary date of when work began under the contract, if the project extends for longer than one year. These changes will assist in clearing ambiguity that could potentially result in inconsistent application of this requirement.
Amendments to §9.24, Performance Review Committee and Actions, replace the term "chairman" with "chair" to align with the language used in 43 TAC §1.1, Texas Transportation Commission.
FISCAL NOTE
Stephen Stewart, Chief Financial Officer, has determined, in accordance with Government Code, §2001.024(a)(4), that for each of the first five years in which the proposed rules are in effect, there will be no fiscal implications for state or local governments as a result of the department's or commission's enforcing or administering the proposed rules.
LOCAL EMPLOYMENT IMPACT STATEMENT
Mr. Duane Milligan, P.E., Director, Construction Division, has determined that there will be no significant impact on local economies or overall employment as a result of enforcing or administering the proposed rules and therefore, a local employment impact statement is not required under Government Code, §2001.022.
PUBLIC BENEFIT
Mr. Duane Milligan, P.E. has determined, as required by Government Code, §2001.024(a)(5), that for each year of the first five years in which the proposed rules are in effect, the public benefit anticipated as a result of enforcing or administering the rules will be streamlining the contract claim process, increasing efficiency in award of contracts for highway projects, and improving clarity and readability of the rules.
COSTS ON REGULATED PERSONS
Mr. Duane Milligan, P.E. has also determined, as required by Government Code, §2001.024(a)(5), that for each year of that period there are no anticipated economic costs for persons, including a state agency, special district, or local government, required to comply with the proposed rules and therefore, Government Code, §2001.0045, does not apply to this rulemaking.
ECONOMIC IMPACT STATEMENT AND REGULATORY FLEXIBILITY ANALYSIS
Mr. Duane Milligan, P.E. has also determined, as required by Government Code, §2001.024(a)(5), that for each year of that period there are no anticipated economic costs for persons, including a state agency, special district, or local government, required to comply with the proposed rules and therefore, Government Code, §2001.0045, does not apply to this rulemaking.
GOVERNMENT GROWTH IMPACT STATEMENT
Mr. Duane Milligan, P.E. has considered the requirements of Government Code, §2001.0221 and anticipates that the proposed rules will have no effect on government growth. He expects that during the first five years that the rule would be in effect:
(1) it would not create or eliminate a government program;
(2) its implementation would not require the creation of new employee positions or the elimination of existing employee positions;
(3) its implementation would not require an increase or decrease in future legislative appropriations to the agency;
(4) it would not require an increase or decrease in fees paid to the agency;
(5) it would not create a new regulation;
(6) it would not expand, limit, or repeal an existing regulation;
(7) it would not increase or decrease the number of individuals subject to its applicability; and
(8) it would not positively or adversely affect this state's economy.
TAKINGS IMPACT ASSESSMENT
Mr. Duane Milligan, P.E. has determined that a written takings impact assessment is not required under Government Code, §2007.043.
SUBMITTAL OF COMMENTS
Written comments on the amendments to §§9.2, 9.15, 9.17, 9.23, and 9.24, may be submitted to Rule Comments, General Counsel Division, Texas Department of Transportation, 125 East 11th Street, Austin, Texas 78701-2483 or to RuleComments@txdot.gov with the subject line "Contract Claims" or "Contracts for Highway Projects." The deadline for receipt of comments is 5:00 p.m. on November 11, 2024. In accordance with Transportation Code, §201.811(a)(5), a person who submits comments must disclose, in writing with the comments, whether the person does business with the department, may benefit monetarily from the proposed amendments, or is an employee of the department.
SUBCHAPTER A. GENERAL
STATUTORY AUTHORITY
The amendments are proposed under Transportation Code, §201.101, which provides the Texas Transportation Commission (commission) with the authority to establish rules for the conduct of the work of the department, and more specifically, Transportation Code, §201.112, which allows the commission by rule to establish procedures for the informal resolution of a claim arising out of a contract under the statutes set forth in that section, and Transportation Code, §223.004, which authorizes the commission to adopt rules to prescribe conditions under which a bid may be rejected by the department.
CROSS REFERENCE TO STATUTES IMPLEMENTED BY THIS RULEMAKING
Transportation Code, §§22.018 and 391.091, and Chapter 223 and Government Code, Chapter 2254, Subchapters A and B.
§9.2.Contract Claim Procedure.
(a) Applicability. A claim shall satisfy the requirements in paragraphs (1) - (3) of this subsection.
(1) The claim is under a contract entered into and administered by the department, acting in its own capacity or as an agent of a local government, under one of the following statutes:
(A) Transportation Code, §22.018 (concerning the designation of the department as agent in contracting and supervising for aviation projects);
(B) Transportation Code, §391.091 (concerning erection and maintenance of specific information logo, major area shopping guide, and major agricultural interest signs);
(C) Transportation Code, Chapter 223 (concerning bids
and contracts for highway [improvement] projects), subject
to the provisions of subsection (c) of this section; or
(D) Government Code, Chapter 2254, Subchapters A and B (concerning professional or consulting services).
(2) The claim is for compensation, or for a time extension, or any other remedy.
(3) The claim is brought by a prime contractor.
(b) Pass-through claim; claim and counter claim.
(1) A prime contractor may make a claim on behalf of a subcontractor only if the prime contractor is liable to the subcontractor on the claim.
(2) Only a prime contractor may submit a claim to begin a claim proceeding under this section. After a claim proceeding has begun the department may make a counter claim.
(3) This section does not abrogate the department's authority to file a claim in a court of competent jurisdiction. The procedure for the department to file a claim in a court of competent jurisdiction, including the deadline to file a claim, is set by other law.
(c) Claim concerning comprehensive development agreement or certain design-build contracts. A claim under a comprehensive development agreement (CDA) entered into under Transportation Code, Chapter 223, Subchapter E, or under a design-build contract, as defined in §9.6 of this subchapter (relating to Contract Claim Procedure for Comprehensive Development Agreements and Certain Design-Build Contracts), may be processed under this section if the parties agree to do so in the CDA or design-build contract, or if the CDA or design-build contract does not specify otherwise. However, if the CDA or design-build contract specifies that a claim procedure authorized by §9.6 of this subchapter applies, then any claim arising under the CDA or design-build contract shall be processed and resolved in accordance with the claim procedure authorized by §9.6 of this subchapter and not by this section.
(d) Definitions. The following words and terms, when used in this section, shall have the following meanings, unless the context clearly indicates otherwise, except that when used in subsection (c) of this section, the terms claim, comprehensive development agreement, CDA, and design-build contract shall have the meanings given such terms stated in §9.6 of this subchapter.
(1) Claim--A claim for compensation, for a time extension, or for any other remedy arising from a dispute, disagreement, or controversy concerning respective rights and obligations under the contract.
(2) Commission--The Texas Transportation Commission.
(3) Committee--The Contract Claim Committee.
(4) Department--The Texas Department of Transportation.
(5) Department office--The department district, division, or office responsible for the administration of the contract.
(6) Department office director--The chief administrative officer of the responsible department office; the officer shall be a district engineer, division director, or office director.
(7) District--One of the 25 districts of the department.
(8) Executive director--The executive director of the Texas Department of Transportation.
(9) Prime contractor--An individual, partnership, corporation, or other business entity that is a party to a written contract with the state of Texas which is entered into and administered by the department under Transportation Code, §22.018, §391.091, Chapter 223, or Government Code, Chapter 2254, Subchapters A and B.
(10) Project--The portion of a contract that can be separated into a distinct facility or work unit from the other work in the contract.
(e) Contract claim committee. The executive director
or the director's designee shall name the members and chair [chairman] of a committee or committees to serve at the executive
director's or designee's pleasure. The chair [chairman]
may add members to the committee, including one or more district engineers
who will be assigned to the committee on a rotating basis, with a
preference, if possible, for district engineers of districts that
do not have a current contractual relationship with the prime contractor
involved in a contract claim.
(f) Negotiated resolution. To every extent possible, disputes between a prime contractor and the department's project engineer should be resolved during the course of the contract.
(g) Procedure.
(1) Exclusive procedure. Except as provided in subsection (c) of this section, a prime contractor shall file a claim under the procedure in this subsection. A claim filed by the prime contractor must be considered first by the committee before the claim is considered in a contested case hearing.
(2) Filing claim.
(A) The prime contractor shall file a claim after completion of the contract or when required for orderly performance of the contract. For a claim resulting from the enforcement of a warranty, a prime contractor shall file the claim no later than one year after expiration of the warranty period. For all other types of claims, a prime contractor shall file the claim no later than one year after the earlier of the date that the department sends to the contractor notice:
(i) that the contractor is in default;
(ii) that the department terminates the contract; or
(iii) notice of final acceptance of the project that is the subject of the contract.
(B) To file a claim, a prime contractor shall file a contract claim request and a detailed report that provides the basis for the claim. The detailed report shall include relevant facts of the claim, cost or other data supporting the claim, a description of any additional compensation requested, and documents supporting the claim. For a request for additional compensation, the prime contractor may not use a method, however denominated, by which the amount requested is determined by subtracting the contractor's bid prices from the contractor's actual performance costs. The prime contractor shall file the claim with the department's construction division, the department engineer under whose administration the contract was or is being performed, or the committee.
(C) A claim filed by a prime contractor shall include a certification as follows: I certify that the claim is made in good faith; that the supporting data are accurate and complete to the best of my knowledge and belief; that the amount requested accurately reflects the contract adjustment for which the contractor believes the department is liable; and that I am duly authorized to certify the claim on behalf of the contractor.
(D) A defective certification shall not deprive the department of jurisdiction over the claim. Prior to the entry by the department of a final decision on the claim the department shall require a defective certification to be corrected.
(E) The construction division or department engineer shall forward the contract claim request and detailed report to the committee.
(F) The deadline for the department to file a counter claim is 45 days before the committee holds an informal meeting under paragraph (3) of this subsection.
(3) Evaluation of claim by the committee.
(A) The committee's responsibility is to gather information, study the relevant issues, and meet informally with the prime contractor if requested. The committee shall attempt to resolve the claim.
(B) The committee shall secure detailed reports and recommendations from the responsible department office, and may confer with any other department office deemed appropriate by the committee. The committee shall give the prime contractor the opportunity to submit a responsive report and recommendation concerning a counter claim filed by the department.
(C) If the department disputes the prime contractor's
claim, the [The] committee shall afford the prime
contractor an opportunity for a meeting to informally discuss the
disputed matters and to provide the prime contractor an opportunity
to present relevant information and respond to information the committee
has received from the department office. The committee chair,
in the chair's sole discretion, may reschedule a meeting. Proceedings
before the committee are an attempt to mutually resolve a claim without
litigation and are not admissible for any purpose in a formal administrative
hearing provided in subparagraph (D)(ii) of this paragraph. All oral
communications, reports, or other written documentation prepared by
department staff in connection with the analysis of a claim are part
of the attempt to mutually resolve a claim without litigation, and
are also not admissible for any purpose in a formal administrative
hearing provided in subparagraph (D)(ii) of this paragraph.
(D) The committee chair [chairman]
shall give written notice of the committee's decision on the claim
to the department and prime contractor. The department and prime contractor
are presumed to receive the decision three days after it is sent by
United States mail.
(i) If the prime contractor does not object to the
committee's decision, the prime contractor shall file a written statement
with the committee's chair [chairman] stating
that the prime contractor does not object. The prime contractor shall
file the statement no later than 20 days after receipt of the committee's
decision. The chair [chairman] shall then prepare
a document showing the settlement of the claim including, when required,
payment to the prime contractor, and the prime contractor's release
of all claims under the contract. The prime contractor shall sign
it. The executive director may approve the settlement, or may request
the commission to approve the settlement by issuance of an order.
The executive director shall then implement the resolution of the
claim. If contemplated in the committee's decision, the executive
director shall expend funds as specified in the decision. If contemplated
in the committee's decision, the executive director shall order the
prime contractor to make payment to the department.
(ii) If the prime contractor objects to the committee's decision the prime contractor shall file a petition with the executive director no later than 20 days after receipt of the committee's decision requesting an administrative hearing to litigate the claim under the provisions of §§1.21 et seq. of this title (relating to Procedures in Contested Cases).
(iii) If the prime contractor fails to file a written
petition under clause (ii) of this subparagraph within 20 days of
receipt of the committee's decision, the prime contractor waives his
right to a contested case hearing. All further litigation of claims
on the project or contract by the prime contractor shall be barred
by the doctrines of issue and claim preclusion. The chair [chairman] shall then prepare an order implementing the resolution
of the claim under the committee's decision, and stating that further
litigation on the claim is prohibited. The executive director shall
then issue the order and implement the resolution of the claim. If
contemplated in the committee's decision, the executive director shall
expend funds as specified in the decision. If contemplated in the
committee's decision, the executive director shall order the prime
contractor to make payment to the department.
(4) Decision after contested case hearing. This paragraph applies if a contested case hearing has been held on a claim. The administrative law judge's proposal for decision shall be submitted to the executive director for adoption. The executive director may change a finding of fact or conclusion of law made by the administrative law judge or may vacate or modify an order issued by the administrative law judge. The executive director shall provide a written statement containing the reason and legal basis for any change.
(5) This section does not abrogate the department's authority to enforce in a court of competent jurisdiction a final department order issued under the section.
(h) Claim forfeiture. A claim against the department shall be forfeited to the department by any person who corruptly practices or attempts to practice any fraud against the department in the proof, statement, establishment, or allowance thereof. In such cases the department shall specifically find such fraud or attempt and render judgment of forfeiture. This subsection applies only if there is clear and convincing evidence that a person knowingly presented a false claim for the purpose of getting paid for the claim.
(i) Relation of contract claim proceeding and sanction proceeding.
(1) Except as provided in paragraphs (2) and (3) of this subsection, the processing of a contract claim under this section is a separate proceeding.
(2) If a contested issue arises that is relevant both to a contract claim proceeding and a sanction proceeding concerning the same contract, the issue shall be resolved in the proceeding that the executive director refers first for a contested case hearing under Chapter 1, Subchapter E of this title (relating to Procedures in Contested Cases). If the issue is decided in the first proceeding that decision shall apply to and be binding in all subsequent department proceedings.
(3) This paragraph applies to a contract under which the parties agreed to submit questions which may arise to the decision of a department engineer. If a dispute under the contract leads to a contract claim proceeding or sanction proceeding, the engineer's decision shall be upheld unless it was based on fraud, misconduct, or such gross mistake as would imply bad faith or failure to exercise an honest judgment.
The agency certifies that legal counsel has reviewed the proposal and found it to be within the state agency's legal authority to adopt.
Filed with the Office of the Secretary of State on September 27, 2024.
TRD-202404664
Becky Blewett
Deputy General Counsel
Texas Department of Transportation
Earliest possible date of adoption: November 10, 2024
For further information, please call: (512) 463-8630
43 TAC §§9.15, 9.17, 9.23, 9.24
STATUTORY AUTHORITY
The amendments are proposed under Transportation Code, §201.101, which provides the Texas Transportation Commission (commission) with the authority to establish rules for the conduct of the work of the department, and more specifically, Transportation Code, §201.112, which allows the commission by rule to establish procedures for the informal resolution of a claim arising out of a contract under the statutes set forth in that section, and Transportation Code, §223.004, which authorizes the commission to adopt rules to prescribe conditions under which a bid may be rejected by the department.
CROSS REFERENCE TO STATUTES IMPLEMENTED BY THIS RULEMAKING
Transportation Code, §§22.018 and 391.091, and Chapter 223 and Government Code, Chapter 2254, Subchapters A and B.
§9.15.Acceptance of Bids.
(a) Public opening. Bids will be opened in accordance with Transportation Code, §223.004 and §223.005.
(1) Bids for contracts, other than building contracts[,] with an estimate of less than $1 million, may
be filed with the district engineer at the headquarters for the district
and opened and read at a public meeting conducted by the district
engineer, or his or her designee, on behalf of the commission.
(2) Bids for a building contract with an estimate of less than $1 million may be filed with the Director of the Support Services Division at the headquarters of the division and opened and read at a public meeting conducted by the director of that division, or the director's designee, on behalf of the commission.
(b) Bids not considered.
(1) The department will not consider a bid if:
(A) the bid is submitted by an unqualified bidder;
(B) the bid is in a form other than the official bid form issued to the bidder;
(C) the certification and affirmation are not signed;
(D) the bid was not in the hands of the letting official at the time and location specified in the advertisement;
(E) the bidder modifies the bid in a manner that alters the conditions or requirements for work as stated in the proposal form;
(F) the bid guaranty, when required, does not comply with §9.14(d) of this subchapter relating to the Submittal of Bid;
(G) the proposal form was signed by a person who was not authorized to bind the bidder or bidders;
(H) the bid does not include a fully completed HUB plan in accordance with §9.356 of this chapter when required;
(I) a typed proposal form does not contain the information in the format shown on the "Example of Bid Prices Submitted by a Computer Printout" in the proposal form;
(J) the bidder was not authorized to be issued a bid form under §9.13(e) of this subchapter relating to Notice of Letting and Issuance of Proposal Forms;
(K) the bid did not otherwise conform with the requirements of §9.14 of this subchapter;
(L) the bidder fails to properly acknowledge receipt of all addenda;
(M) the bid submitted has the incorrect number of bid items;
(N) the bidder does not meet the applicable technical qualification requirements;
(O) the bidder fails to submit a DBE commitment within the period described by §9.17(i) of this subchapter relating to Award of Contract;
(P) the bidder fails to meet the requirements of §9.17(j) of this chapter relating to participation in the Department of Homeland Security (DHS) E-Verify system; or
(Q) the bidder bids more than the maximum or less than the minimum number of allowable working days shown on the plans when working days is a bid item.
(2) If bids are submitted on the same project separately by a joint venture and one or more members of that joint venture, the department will not accept any of the bids submitted by the joint venture and those members for that project.
(3) If bids are submitted on the same project by affiliated bidders as determined under §9.27 of this subchapter (relating to Affiliated Entities) and the executive director has not granted an affiliation exception under §9.12(g) of this subchapter relating to the Qualification of Bidders, the department will not accept any of the bids submitted by the affiliated bidders for that project.
(c) Revision of bid.
(1) For a manually submitted bid, a bidder may change a bid price before it is submitted to the department by changing the price in the printed bid form and initialing the revision in ink;
(2) For a manually submitted bid, a bidder may change a bid price after it is submitted to the department by requesting return of the bid in writing prior to the expiration of the time for receipt of bids, as stated in the advertisement. The request must be made by a person authorized to bind the bidder. The department will not accept a request by telephone but will accept a properly signed facsimile request. The revised bid must be resubmitted prior to the time specified for the close of the receipt of bids.
(3) For an electronically submitted bid, a bidder may change a unit bid price in EBS and resubmit electronically to the electronic vault until the time specified for the close of the receipt of bids. Each bid submitted will be retained in the electronic vault. The electronic bid with the latest date and time stamp by the vault will be used for bid tabulation purposes.
(d) Withdrawal of bid.
(1) A bidder may withdraw a manually submitted bid
by submitting a request in writing to the letting official before
the time and date of the bid opening. The request must be made by
a person authorized to bind the bidder. The department will not accept
telephone requests[,] but will accept a properly signed
facsimile request. Except as provided in §9.16(c) of this subchapter
relating to Tabulation of Bids and §9.17(d) of this subchapter,
a bidder may not withdraw a bid subsequent to the time for the receipt
of bids.
(2) A bidder may withdraw an electronically submitted bid by submitting an electronic or written request to withdraw the bid. An electronic withdrawal request must be submitted using EBS. The request, whether electronic or written, must be submitted by a person who is authorized by the bidder to submit the request and received by the department before the time and date of the bid opening.
(e) Unbalanced bids. The department will examine the
unit bid prices of the apparent low bid for reasonable conformance
with the department's estimated prices. The department will evaluate an apparent low [a] bid with extreme variations from
the department's estimate or where obvious unbalancing of unit prices
has occurred. For the purposes of the evaluation, the department
will presume the same retainage percentage for all bidders. The
department may consider an apparent low bid nonresponsive if [In the event that] the evaluation of the unit bid prices reveals
that the apparent low bid is mathematically and materially unbalanced
[, the bidder will not be considered in future bids for the same
project].
§9.17.Award of Contract.
(a) The commission may reject any and all bids opened, read, and tabulated under §9.15 and §9.16 of this subchapter (relating to Acceptance of Bids and Tabulation of Bids, respectively). It will reject all bids if:
(1) there is reason to believe collusion may have existed among the bidders;
(2) [the lowest bid is determined to be both mathematically
and materially unbalanced;]
[(3)] the lowest bid is higher than the
department's estimate and the commission determines that re-advertising
the project for bids may result in a significantly lower low bid;
(3) [(4)] the lowest bid is higher
than the department's estimate and the commission determines that
the work should be done by department forces; or
(4) [(5)] the lowest bid is determined
to contain a bid error that meets the notification requirements contained
in §9.16(e)(1) of this subchapter and satisfies the criteria
contained in §9.16(e)(2) of this subchapter.
(b) Except as provided in subsection (c), (d), (e), or (f) of this section, if the commission does not reject all bids, it will award the contract to the lowest bidder.
(c) In accordance with Government Code, Chapter 2252, Subchapter A, the commission will not award a contract to a nonresident bidder unless the nonresident underbids the lowest bid submitted by a responsible resident bidder by an amount that is not less than the greater of:
(1) the amount by which a resident bidder would be required to underbid the nonresident bidder to obtain a comparable contract in the state in which:
(A) the nonresident's principal place of business is located; or
(B) the nonresident is a resident manufacturer; or
(2) the amount by which a resident bidder would be required to underbid the nonresident bidder to obtain a comparable contract in the state in which a majority of the manufacturing related to the contract will be performed.
(d) For a maintenance contract for a building or a segment of the state highway system involving a bid amount of less than $300,000, if the lowest bidder withdraws its bid after bid opening, the executive director may recommend to the commission that the contract be awarded to the second lowest bidder.
(1) For purposes of this subsection, the term "withdrawal" includes written withdrawal of a bid after bid opening, failure to provide the required insurance or bonds, or failure to execute the contract.
(2) The executive director may recommend award of the contract to the second lowest bidder if he or she, in writing, determines that the second lowest bidder is willing to perform the work at the unit bid prices of the lowest bidder; and
(A) the unit bid prices of the lowest bidder are reasonable, and delaying award of the contract may result in significantly higher unit bid prices;
(B) there is a specific need to expedite completion of the project to protect the health or safety of the traveling public; or
(C) delaying award of the contract would jeopardize the structural integrity of the highway system.
(3) The commission may accept the withdrawal of the lowest bid after bid opening if it concurs with the executive director's determinations.
(4) If the commission awards a contract to the second lowest bidder and the department successfully enters into a contract with the second lowest bidder, the department will return the lowest bidder's bid guaranty upon execution of that contract.
(e) If the lowest bidder is not a preferred bidder and the contract will not use federal funds, the department, in accordance with Transportation Code, Chapter 223, Subchapter B, will award the contract to the lowest-bidding preferred bidder if that bidder's bid does not exceed the amount equal to 105 percent of the lowest bid. For purposes of this subsection, "preferred bidder" means a bidder whose principal place of business is in this state or a state that borders this state and that does not give a preference similar to Transportation Code, §223.050.
(f) When additional information is required to make a final decision, the commission may defer the award or rejection of the contract until the next regularly scheduled commission meeting.
(g) Contracts with an engineer's estimate of less than $1 million may be awarded or rejected by the executive director under the same conditions and limitations as provided in subsections (a)-(c) of this section.
(h) The commission may rescind the award of any contract prior to contract execution upon a determination that it is in the best interest of the state. The executive director may rescind the award of a contract awarded under subsection (g) of this section prior to contract execution upon a determination that it is in the best interest of the state. If a contract is rescinded under this subsection, the bid guaranty will be returned to the bidder but no compensation will be paid to the bidder as a result of the rescission.
(i) For a contract with a DBE goal, all bidders must
submit the DBE information required by §9.227 of this chapter
(relating [related] to Information from Bidders)
within five calendar days after the date that the bids are opened.
(j) Prior to contract award, all low bidders must be participating or provide documentation of participation in the Department of Homeland Security's (DHS) E-Verify system within five calendar days after the date that the bids are opened.
§9.23.Evaluation and Monitoring of Contract Performance.
(a) The department will develop standards used to evaluate a contractor's performance under a highway improvement contract, including standards for conformance with the project plans and specifications and recordkeeping requirements; compliance with the contract and industry standards for safety; responsiveness in dealing with the department and the public; meeting progress benchmarks and project milestones; addressing project schedule issues, given adjustments, change orders, and unforeseen conditions or circumstances; and completing project on time. The department will develop an evaluation form to be used by department employees in evaluating contract performance.
(b) The district engineer of the district in which
a project under a highway improvement contract, other than a building
contract, is located, or the Director of the Support Services Division
for building contracts, shall evaluate the contractor's
performance under the contract. An interim evaluation shall be performed
as necessary and [on each anniversary date of the contract]
if the project extends for longer than one year, on each anniversary
of the date that work began under the contract. The district
engineer for a highway improvement contract, other than a building
contract, or the Director of the Support Services Division for a building
contract, shall approve any final evaluations on the completion
of the project. Only final evaluations will be used to determine whether
the contractor's contract performance meets the department's requirements.
(c) If the contractor's performance on a project is below the department's acceptable standards for contract performance, the district engineer or the Director of the Support Services Division, as applicable, may work with the contractor to establish a recovery plan for the project. The established project recovery plan will be used to correct significant deficiencies in contractor performance. The district engineer or the Director of the Support Services Division, as applicable, will monitor and document the contractor's compliance with the established project recovery plan.
(d) For a highway improvement contract, other than a building contract, the district engineer will submit the final evaluation scores performed under this section to the division of the department that is responsible for monitoring the contract.
(e) The division that monitors the final evaluation scores of a contractor periodically will review the final evaluation scores of that contractor that were completed during the review period, or if fewer than 10 final evaluations were completed during the review period, up to 10 of the most recent final evaluations completed within the previous three-year period. If the average of the final evaluation scores reviewed is below the department's acceptable standards for contract performance, the division will send a notice to the contractor and request that the contractor submit to the division for approval a proposed corrective action plan that will be used to correct significant deficiencies in the performance in all of the contractor's projects. The division, in consultation with the department's Chief Engineer for a highway improvement contract, other than a building contract, or the Director of the Support Services Division for a building contract, may modify the proposed corrective action plan and adopt a final plan. The division promptly will send the adopted corrective action plan to the contractor.
(f) For the 120-day period beginning on the day that the adopted corrective action plan is sent under subsection (e) of this section, the division will monitor the contractor's active projects to determine whether the contractor is meeting the requirements of the adopted corrective action plan, or if there are no active projects, the division will monitor the contractor's next available projects. Before making a determination under this subsection, the division must consider and document any events outside a contractor's control that contributed to the contractor's failure to meet the performance standards or failure to comply with the corrective action plan. If at the end of the 120-day period contract performance remains below the department's standards for contract performance, the division will notify the contractor and forward to the Performance Review Committee all of the information that it has, which includes at minimum all final evaluations, any adopted corrective action plans, and any information about events outside a contractor's control contributing to the contractor's performance.
§9.24.Performance Review Committee and Actions.
(a) If information is required to be forwarded to a
Performance Review Committee under §9.23 of this subchapter (relating
to Evaluation and Monitoring of Contract Performance) or if a contractor,
including a contractor on a materials contract, has defaulted, the
deputy executive director will appoint the members and chair [chairman] of the Performance Review Committee. The members and chair [chairman] serve at the discretion of the deputy
executive director. The Performance Review Committee will review the
information submitted to the committee under §9.23(f) of this
subchapter, any documentation developed by the department during the
evaluation process under §9.23 of this subchapter, and any documentation
submitted by the contractor. For a materials contract, the Performance
Review Committee will review any documentation developed by the department
related to the contract and any documentation submitted by the contractor.
The committee will determine whether grounds exist for action under
this section. After reviewing the submitted information, the Performance
Review Committee may recommend one or more of the following:
(1) take no action;
(2) reduce the contractor's bidding capacity;
(3) prohibit the contractor from bidding on one or more projects;
(4) immediately suspend the contractor from bidding for a specified period of time; or
(5) prohibit the contractor from being awarded a contract on which they are the apparent low bidder.
(b) The Performance Review Committee may recommend that one or more actions listed in subsection (a) of this section be taken immediately to ensure project quality, safety, or timeliness if:
(1) the contractor failed to execute a highway improvement contract or a materials contract after a bid is awarded, unless the contractor honored the bid guaranty submitted under §9.14(d) of this chapter (relating to Submittal of Bid);
(2) the commission, during the preceding 36-month period, rejected two or more bids by the contractor because of contractor error;
(3) the department declared the contractor in default on a highway improvement contract or a materials contract; or
(4) a district notifies the committee through the referring division that a contractor has failed to comply with a project recovery plan established under §9.23(c) of this subchapter.
(c) If the Performance Review Committee determines that one or more actions listed in subsection (a) of this section is appropriate, the committee may recommend that the action or actions also be taken against an entity that the committee determines, in accordance with §9.27 of this subchapter (relating to Affiliated Entities), is affiliated with the contractor.
(d) If the Performance Review Committee determines that action under subsection (a), (b), or (c) of this section is appropriate, the committee, except as provided by subsection (g) of this section, will confer with the Chief Engineer, or the Chief Administrative Officer for a building contract, on the appropriate action to be taken and applied to the contractor. The committee will send its recommendation to the Deputy Executive Director within 10 business days after the date that it determines the action to be applied.
(e) The Deputy Executive Director will consider the Performance Review Committee's recommendation and make a determination of any action to be taken. Within 10 business days after the date of the Deputy Executive Director's determination, the department will send notice to the contractor and to appropriate department employees affected by the determination. The notice will:
(1) state the nature and extent of the remedial action;
(2) summarize the facts and circumstances underlying the action;
(3) explain how the remedial action was determined;
(4) if applicable, inform the entity of the imposition of a suspension; and
(5) state that the provider may appeal the reduction in accordance with §9.25 of this subchapter (relating to Appeal of Remedial Action).
(f) A decision of the Deputy Executive Director under
subsection (e) of this section may be appealed in accordance with
§9.25 of this title [relating to Appeal of Remedial Action].
(g) If the Performance Review Committee, in the performance of its duties under this section finds information that indicates that grounds for the imposition of sanctions under Chapter 10 of this title (relating to Ethical Conduct by Entities Doing Business with the Department) may exist, the committee immediately shall provide that information to the department's Compliance Division.
The agency certifies that legal counsel has reviewed the proposal and found it to be within the state agency's legal authority to adopt.
Filed with the Office of the Secretary of State on September 26, 2024.
TRD-202404632
Becky Blewett
Deputy General Counsel
Texas Department of Transportation
Earliest possible date of adoption: November 10, 2024
For further information, please call: (512) 463-8630
The Texas Department of Transportation (department) proposes amendments to §9.152 and §9.153 concerning Design Build Contracts.
EXPLANATION OF PROPOSED AMENDMENTS
House Bill 2830, 86th Legislature, 2019, amended Transportation Code, Chapter 223, Subchapter F, which authorizes the department to enter into a design-build contract for a highway project, and prescribes the procurement process to be followed by the department for a design-build contract.
House Bill 2830 revised the limitation on the number of design-build contracts that may be entered into by the department to no more than six contracts each fiscal biennium, and amended Transportation Code, §223.246(a), to require a request for proposals for a design-build project to include a design, rather than a schematic design, that is approximately 30 percent complete.
Amendments to §9.152, General Rules for Design-Build Contracts, clarify that the department's reserved rights in administering a procurement for a design-build project includes the right to suspend the procurement. Because of project delays or for other reasons, the department may need to suspend the procurement for a design-build project.
Transportation Code, §223.246(a)(5), previously required a request for proposals to include a schematic design that is approximately 30 percent complete. In general, a schematic design that is 100% complete is comparable to a design that is approximately 30 percent complete.
Amendments to §9.153, Solicitation of Proposals, implement the changes made by House Bill 2830 by providing that a request for proposals must include a design that is approximately 30 percent complete. This change provides the department with the flexibility to develop a project with enough detail to aid the procurement process, cost estimation, and understanding of contractor and department risk.
Transportation Code, §223.249, provides that in a request for proposals, the department shall provide for the payment of a partial stipend in the event that a procurement is terminated before the execution of a design-build contract. As the Texas Constitution generally prohibits grants of public funds, payment of stipends to proposers without receiving work product in exchange would raise constitutional issues. The amendments to §9.153(f) clarify that, if a procurement is terminated, a partial payment will be paid to an unsuccessful proposer that submits a proposal responsive to the requirements of the request for proposals. The partial payment would be made in exchange for the work product in the proposal. The amendments allow the department to request that a proposer submit to the department work product that was developed by the proposer for a project if the procurement for the project is terminated before receipt of proposals. A partial payment for that work product may be made if the department determines that the requested work product was developed in accordance with the requirements of the request for proposals and can be used by the department in the performance of its functions. In all cases, the amount of the payment to a proposer will not exceed the value of the work product to the department, as determined by the department.
FISCAL NOTE
Stephen Stewart, Chief Financial Officer, has determined, in accordance with Government Code, §2001.024(a)(4), that for each of the first five years in which the proposed rules are in effect, there will be no fiscal implications for state or local governments as a result of enforcing or administering the amendments.
LOCAL EMPLOYMENT IMPACT STATEMENT
Gregory Snider, P.E., Director, Alternative Delivery Division has determined that there will be no significant impact on local economies or overall employment as a result of enforcing or administering the proposed rules and therefore, a local employment impact statement is not required under Government Code, §2001.022.
PUBLIC BENEFIT
Mr. Snider has determined, as required by Government Code, §2001.024(a)(5), that for each year of the first five years in which the proposed rules are in effect, the public benefit anticipated as a result of enforcing or administering the rules will be to facilitate the implementation of an efficient procurement process for design-build contracts, thereby allowing the department to enhance competition in procurements and to obtain the best value for the department.
COSTS ON REGULATED PERSONS
Mr. Snider has also determined, as required by Government Code, §2001.024(a)(5), that for each year of that period there are no anticipated economic costs for persons, including a state agency, special district, or local government, required to comply with the proposed rules and therefore, Government Code, §2001.0045, does not apply to this rulemaking.
ECONOMIC IMPACT STATEMENT AND REGULATORY FLEXIBILITY ANALYSIS
There will be no adverse economic effect on small businesses, micro-businesses, or rural communities, as defined by Government Code, §2006.001, and therefore, an economic impact statement and regulatory flexibility analysis are not required under Government Code, §2006.002.
GOVERNMENT GROWTH IMPACT STATEMENT
Mr. Snider has considered the requirements of Government Code, §2001.0221 and anticipates that the proposed rules will have no effect on government growth. He expects that during the first five years that the rule would be in effect:
(1) it would not create or eliminate a government program;
(2) its implementation would not require the creation of new employee positions or the elimination of existing employee positions;
(3) its implementation would not require an increase or decrease in future legislative appropriations to the agency; (4) it would not require an increase or decrease in fees paid to the agency;
(5) it would not create a new regulation;
(6) it would not expand, limit, or repeal an existing regulation;
(7) it would not increase or decrease the number of individuals subject to its applicability; and
(8) it would not positively or adversely affect this state's economy.
TAKINGS IMPACT ASSESSMENT
Mr. Snider has determined that a written takings impact assessment is not required under Government Code, §2007.043.
SUBMITTAL OF COMMENTS
Written comments on the amendments to §9.152 and §9.153 may be submitted to Rule Comments, General Counsel Division, Texas Department of Transportation, 125 East 11th Street, Austin, Texas 78701-2483 or to RuleComments@txdot.gov with the subject line "Design-Build Procurements." The deadline for receipt of comments is 5:00 p.m. on November 11, 2024. In accordance with Transportation Code, §201.811(a)(5), a person who submits comments must disclose, in writing with the comments, whether the person does business with the department, may benefit monetarily from the proposed amendments, or is an employee of the department.
STATUTORY AUTHORITY
The amendments are proposed under Transportation Code, §201.101, which provides the Texas Transportation Commission (commission) with the authority to establish rules for the conduct of the work of the department.
CROSS REFERENCE TO STATUTES IMPLEMENTED BY THIS RULEMAKING
Transportation Code, Chapter 223, Subchapter F.
§9.152.General Rules for Design-Build Contracts.
(a) Applicability. The rules in this subchapter address the manner by which the department intends to evaluate submissions received from private entities in response to requests for qualifications and requests for proposals issued by the department.
(b) Reservation of rights. The department reserves all rights available to it by law in administering this subchapter, including without limitation the right in its sole discretion to:
(1) withdraw a request for qualifications or a request for proposals at any time, and issue a new request;
(2) reject any and all qualifications submittals or proposals at any time;
(3) terminate evaluation of any and all qualifications submittals or proposals at any time;
(4) suspend, discontinue, or terminate negotiations with any proposer at any time prior to the actual authorized execution of a design-build contract by all parties;
(5) negotiate with a proposer without being bound by any provision in its proposal;
(6) negotiate with a proposer to include aspects of unsuccessful proposals for that project in the design-build contract;
(7) request or obtain additional information about any proposal from any source;
(8) suspend a procurement or modify, issue addenda to, or cancel any request for qualifications or request for proposals;
(9) waive deficiencies in a qualifications submittal or proposal, accept and review a non-conforming qualifications submittal or proposal, or permit clarifications or supplements to a qualifications submittal or proposal; or
(10) revise, supplement, or make substitutions for all or any part of this subchapter.
(c) Costs incurred by proposers. Except as provided in §9.153(f) of this subchapter (relating to Solicitation of Proposals), under no circumstances will the state, the department, or any of their agents, representatives, consultants, directors, officers, or employees be liable for, or otherwise obligated to reimburse, the costs incurred by proposers, whether or not selected for negotiations, in developing proposals or in negotiating agreements.
(d) Department information. Any and all information the department makes available to proposers shall be as a convenience to the proposer and without representation or warranty of any kind except as may be expressly specified in the request for qualifications or request for proposals. Proposers may not rely upon any oral responses to inquiries.
(e) Procedure for communications. If a proposer has a question or request for clarification regarding this subchapter or any request for qualifications or request for proposals issued by the department, the proposer shall submit the question or request for clarification in writing to the person responsible for receiving those submissions, as designated in the request for qualifications or request for proposals, and the department will provide the responses in writing. The proposer shall also comply with any other provisions in the request for qualifications or request for proposals regulating communications.
(f) Compliance with rules. In submitting any proposal, the proposer shall be deemed to have unconditionally and irrevocably consented and agreed to the foregoing provisions and all other provisions of this subchapter.
(g) Proposer information submitted to department. All qualifications submittals or proposals submitted to the department become the property of the department and may be subject to the Public Information Act, Government Code, Chapter 552. Proposers should familiarize themselves with the provisions of the Public Information Act. In no event shall the state, the department, or any of their agents, representatives, consultants, directors, officers, or employees be liable to a proposer for the disclosure of all or a portion of a proposal submitted under this subchapter. Except as otherwise expressly specified in the request for qualifications or request for proposals, if the department receives a request for public disclosure of all or any portion of a qualifications submittal or proposal, the department will notify the applicable proposer of the request and inform that proposer that it has an opportunity to assert, in writing, a claimed exception under the Public Information Act or other applicable law within the time period specified in the department's notice and allowed under the Public Information Act. If a proposer has special concerns about information it desires to make available to the department, but which it believes constitutes a trade secret, proprietary information or other information excepted from disclosure, the proposer should specifically and conspicuously designate that information as such in its qualifications submittal or proposal. The proposer's designation shall not be dispositive of the trade secret, proprietary, or exempted nature of the information so designated.
(h) Sufficiency of proposal. All proposals, whether solicited or unsolicited, should be as thorough and detailed as possible so that the department may properly evaluate the potential feasibility of the proposed project as well as the capabilities of the proposer and its team members to provide the proposed services and complete the proposed project.
(i) Project studies. Studies that the department deems necessary as to route designation, civil engineering, environmental compliance, and any other matters will be assigned, conducted, and paid for as negotiated between the department and the successful proposer and set forth in the design-build contract.
(j) Proposer's additional responsibilities. The department, in its sole discretion, may authorize the successful proposer to seek licensing, permitting, approvals, and participation required from other governmental entities and private parties, subject to such oversight and review by the department as specified in the design-build contract.
(k) Proposer's work on environmental review of eligible project. The department may solicit proposals in which the proposer is responsible for providing assistance in the environmental review and clearance of an eligible project, including the provision of technical assistance and technical studies to the department or its environmental consultant relating to the environmental review and clearance of the proposed project. The environmental review and the documentation of that review shall at all times be conducted as directed by the department and subject to the oversight of the department, and shall comply with all requirements of state and federal law, applicable federal regulations, and the National Environmental Policy Act (42 U.S.C. §4321 et seq.), if applicable, including but not limited to the study of alternatives to the proposed project and any proposed alignments, procedural requirements, and the completion of any and all environmental documents required to be completed by the department and any federal agency acting as a lead agency. The department:
(1) shall determine the scope of work to be performed by the private entity or its consultants or subcontractors;
(2) shall specify the level of design and other information to be provided by the private entity or its consultants or subcontractors; and
(3) shall independently review any studies and conclusions reached by the private entity or its consultants or subcontractors before their inclusion in an environmental document.
(l) Effect of environmental requirements on design-build contract. Completion of the environmental review, including obtaining approvals required under the National Environmental Policy Act, is required before the private entity may be authorized to conduct and complete the final design and start construction of a project. Additionally, all applicable state and federal environmental permits and approvals must be obtained before the private entity may start construction of the portion of a project requiring the permit or approval. Unless and until that occurs, the department is not bound to any further development of the project. The department, and any federal agency acting as a lead agency, may select an alternative other than the one in the proposed project, including the "no-build" alternative. A design-build contract shall provide that the agreement will be modified as necessary to address requirements in the final environmental documents and shall provide that the agreement may be terminated if the "no-build" alternative is selected or if another alternative is selected that is incompatible with the requirements of the agreement.
(m) Public meetings and hearings. All public meetings or hearings required to be held under applicable law or regulation will be directed and overseen by the department, with participation by such other parties as it deems appropriate.
(n) Additional matters. Any matter not specifically addressed in this subchapter that pertains to the construction, expansion, extension, related maintenance, rehabilitation, alteration, or repair of a highway project pursuant to this subchapter, shall be deemed to be within the primary purview of the commission, and all decisions pertaining thereto, whether or not addressed in this subchapter, shall be as determined by the commission, subject to the provisions of applicable law.
(o) Performance and payment security. The department shall require a private entity entering into a design-build contract to provide a performance and payment bond or an alternative form of security, or a combination of bonds and other forms of security, in an amount equal to the cost of constructing the project, unless the department determines that it is impracticable for a private entity to provide security in that amount, in which case the department will set the amount of security. The security will be in the amount that, in the department's sole determination, is sufficient to ensure the proper performance of the agreement, and to protect the department and payment bond beneficiaries supplying labor or materials to the private entity or a subcontractor of the private entity. Bonds and alternate forms of security shall be in the form and contain the provisions required in the request for proposals or the design-build contract, with such changes or modifications as the department determines to be in the best interest of the state. In addition to, or in lieu of, performance and payment bonds, the department may require:
(1) a cashier's check drawn on a federally insured financial institution, and drawn to the order of the department;
(2) United States bonds or notes, accompanied by a duly executed power of attorney and agreement authorizing the collection or sale of the bonds or notes in the event of the default of the private entity or a subcontractor of the private entity, or such other act or event that, under the terms of the design-build contract, would allow the department to draw upon or access that security;
(3) an irrevocable letter of credit issued or confirmed by a financial institution to the benefit of the department, meeting the credit rating and other requirements prescribed by the department, and providing coverage for a period of at least one year following final acceptance of the project or, if there is a warranty period, at least one year following completion of the warranty period;
(4) an irrevocable letter signed by a guarantor meeting the net worth or other financial requirements prescribed in the request for proposals or design-build contract, and which guarantees, to the extent required under the request for proposals or design-build contract, the full and prompt payment and performance when due of the private entity's obligations under the design-build contract; or
(5) any other form of security deemed suitable by the department.
(p) Performance evaluations. The department will evaluate the performance of a private entity that enters into a design-build contract and will evaluate the performance of the private entity's major team members, consultants, and subcontractors, in accordance with the requirements of this subsection. Evaluations will be conducted annually at twelve month intervals during the term of the design-build contract, upon termination of the design-build contract, and when the department determines that work is materially behind schedule or not being performed according to the requirements of the design-build contract. Optional evaluations may be conducted as provided in the design-build contract. Acts or omissions that are the subject of a good faith dispute will not be considered. After a performance evaluation is conducted, and for at least 30 days before the evaluation becomes final and is used by the department, the department will provide for review and comment a copy of the performance evaluation report to the entity being evaluated and, if that entity is a consultant or subcontractor, to the entity that entered into the design-build contract. The department will consider and take into account any submitted comments before the department finalizes the performance evaluation report. The results of performance evaluations will be provided to the entity that was evaluated and may be used in the evaluation of qualifications submittals and proposals submitted under §9.153 of this subchapter and §27.4 of this title (relating to Solicited Proposals) by proposers that include the major team members, consultants, and subcontractors evaluated.
§9.153.Solicitation of Proposals.
(a) Request for qualifications-notice. If authorized by the commission to issue a request for qualifications for a highway project, the department will set forth the basic criteria for qualifications, experience, technical competence and ability to develop the project, and such other information as the department considers relevant or necessary in the request for qualifications. The department will publish notice advertising the issuance of the request for qualifications in the Texas Register and will post the notice and the request for qualifications on the department's Internet website. The department may also elect to furnish the request for qualifications to businesses in the private sector that the department otherwise believes might be interested and qualified to participate in the project that is the subject of the request for qualifications.
(b) Request for qualifications-content. At its sole option, the department may elect to furnish conceptual designs, fundamental details, technical studies and reports or detailed plans of the proposed project in the request for qualifications and may request conceptual approaches to bringing the project to fruition. A request for qualifications must include:
(1) information regarding the proposed project's location, scope, and limits;
(2) information regarding funding that may be available for the project;
(3) criteria that will be used to evaluate the qualifications submittals;
(4) the relative weight to be given to the criteria;
(5) the deadline by which qualifications submittals must be received by the department; and
(6) any other information the department considers relevant or necessary.
(c) Request for qualifications-evaluation. The department, after evaluating the qualification submittals received in response to a request for qualifications, will identify and approve a "short-list" that is composed of those entities that are considered most qualified to submit detailed proposals for a proposed project. In evaluating the qualification submittals, the department will consider the results of performance evaluations conducted by the department under §9.152 of this subchapter (relating to General Rules for Design-Build Contracts) and §27.3 of this title (relating to General Rules for Private Involvement) determined by the department to be relevant to the project, the results of other performance evaluations determined by the department to be relevant to the project, and other objective evaluation criteria that the department considers relevant to the project, including a proposer's qualifications, experience, technical competence, and ability to develop the project, and that may include the private entity's financial condition, management stability, staffing, and organizational structure. The department may interview entities responding to a request for qualifications. The department shall short-list at least two private entities to submit proposals but may not short-list more private entities than the number of private entities designated in the request for qualifications if a maximum number is designated. The department shall advise each entity providing a qualifications submittal whether it is on the short-list of qualified entities.
(d) Requests for proposals. If authorized by the commission, the department will issue a request for proposals from all private entities qualified for the short-list, consisting of the submission of detailed documentation regarding the project. A request for proposals must include:
(1) information on the overall project goals;
(2) publicly available cost estimates for the design-build portion of the project;
(3) materials specifications;
(4) special material requirements;
(5) a [schematic] design approximately 30
percent complete;
(6) known utilities;
(7) quality assurance and quality control requirements;
(8) the location of relevant structures;
(9) notice of any rules or goals adopted by the department relating to awarding contracts to disadvantaged business enterprises or small business enterprises;
(10) available geotechnical or other information related to the project;
(11) the status of any environmental review of the project;
(12) detailed instructions for preparing the technical proposal, including a description of the form and level of completeness of drawings expected;
(13) the relative weighting of the technical and cost proposals and the formula by which the proposals will be evaluated and ranked, which must allocate at least 70 percent of weighting to the cost proposal;
(14) the criteria to be used in evaluating the technical proposals, and the relative weighting of those criteria;
(15) the proposed form of design-build contract; and
(16) any other information the department considers relevant or necessary.
(e) Request for proposals-submittal requirements. The request for proposals must require the submission of a sealed technical proposal and a separate sealed cost proposal no later than the 180th day after the issuance of the request for proposals, and that provide information relating to:
(1) the feasibility of developing the project as proposed;
(2) the proposed solutions to anticipated problems;
(3) the ability of the proposer to meet schedules;
(4) the engineering design proposed;
(5) the cost of delivering the project;
(6) if maintenance of the project is required, pricing for the maintenance work for each maintenance term;
(7) the estimated number of days required to complete the project; and
(8) any other information requested by the department.
(f) Requests for proposals-payment for work product.
The request for proposals shall stipulate an amount of money, as authorized
under Transportation Code, §223.249, that the department will
pay to an unsuccessful proposer that submits a proposal that is responsive
to the requirements of the request for proposals. The commission shall
approve the amount of the payment to be stipulated in the request
for proposals, which must be a minimum of twenty-five hundredths of
one percent of the contract amount. The request for proposals shall
provide for the payment of a partial amount in the event the procurement
is terminated. A partial amount will be paid to an unsuccessful
proposer that submits a proposal that is responsive to the requirements
of the request for proposals. If the procurement is terminated prior
to the receipt of proposals, the department may request that a proposer
submit to the department work product that was developed by the proposer
for the project for the purpose of paying a partial amount. If the
department determines, in its discretion, that the requested work
product was developed in accordance with the requirements of the request
for proposals and can be used by the department in the performance
of its functions, the department will pay the proposer a partial amount
not exceeding the value of the work product to the department, as
determined by the department. In determining the amount of a [the] payment, the commission shall consider:
(1) the effect of a payment on the department's ability to attract meaningful proposals and to generate competition;
(2) the work product expected to be included in the proposal and the anticipated value of that work product; and
(3) the costs anticipated to be incurred by a private entity in preparing a proposal.
(g) Request for proposals-evaluation. The proposals will be evaluated by the department based on the results of performance evaluations conducted by the department under §9.152 of this subchapter and §27.3 of this title determined by the department to be relevant to the project, the results of other performance evaluations determined by the department to be relevant to the project, and other objective evaluation criteria the department deems appropriate for the project, including those criteria deemed appropriate by the department to maximize the overall performance of the project and the resulting benefits to the state. Specific evaluation criteria and requests for pertinent information will be set forth in the request for proposals. The department shall first open, evaluate, and score each responsive technical proposal, and shall subsequently open, evaluate, and score the cost proposals from proposers that submitted a responsive technical proposal and assign points on the basis of the weighting specified in the request for proposals.
(h) Apparent best value proposal. Based on the evaluation using the evaluation criteria described under subsection (g) of this section and set forth in the request for proposals, the department will rank all proposals that are complete, responsive to the request for proposals, and in conformance with the requirements of this subchapter, in accordance with the formula provided in the request for proposals. The department may select the private entity whose proposal offers the apparent best value to the department.
(i) Selection of entity. The department shall submit a recommendation to the commission regarding approval of the proposal determined to provide the apparent best value to the department. The commission may approve or disapprove the recommendation, and if approved, will award the design-build contract to the apparent best value proposer. Award may be subject to the successful completion of negotiations, any necessary federal action, execution by the executive director of the design-build contract, and satisfaction of such other conditions that are identified in the request for proposals or by the commission. The proposers will be notified in writing of the department's rankings. The department shall also make the rankings available to the public.
(j) Negotiations with selected entity. If authorized by the commission, the department will attempt to negotiate a design-build contract with the apparent best value proposer. If a design-build contract satisfactory to the department cannot be negotiated with that proposer, or if, in the course of negotiations, it appears that the proposal will not provide the department with the overall best value, the department will formally and in writing end negotiations with that proposer and, in its sole discretion, either:
(1) reject all proposals;
(2) modify the request for proposals and begin again the submission of proposals; or
(3) proceed to the next most highly ranked proposal and attempt to negotiate a design-build contract with that entity in accordance with this paragraph.
The agency certifies that legal counsel has reviewed the proposal and found it to be within the state agency's legal authority to adopt.
Filed with the Office of the Secretary of State on September 26, 2024.
TRD-202404631
Becky Blewett
Deputy General Counsel
Texas Department of Transportation
Earliest possible date of adoption: November 10, 2024
For further information, please call: 512-463-8630
SUBCHAPTER A. GENERAL
The Texas Department of Transportation (department) proposes the repeal of §13.8, relating to Testing Asphalt.
EXPLANATION OF PROPOSED REPEAL
During the periodic rule review, the department determined that the procedure set out in §13.8 is obsolete. The rule was adopted in 1991 to encourage asphalt binder suppliers to provide products that consistently comply with the department's specifications. Over the years, the department's Asphalt Binder Quality Program has been continually strengthened to ensure that the quality of asphalt binder products used on the department's projects meets the department's specifications. The program preemptively ensures consistency by requiring suppliers to share their data and updates with the department, enforces compliance through suspension or disqualifications, and ensures transparency. This approach more effectively encourages suppliers to comply with department's specifications than the approach provided by §13.8.
Section §13.8, Testing Asphalt, is repealed.
FISCAL NOTE
Stephen Stewart, Chief Financial Officer, has determined, in accordance with Government Code, §2001.024(a)(4), that for each of the first five years in which the proposed rule is in effect, there will be no fiscal implications for state or local governments as a result of the department's or commission's enforcing or administering the proposed rule.
LOCAL EMPLOYMENT IMPACT STATEMENT
Duane Milligan, P.E. Director, Construction Division, has determined that there will be no significant impact on local economies or overall employment as a result of enforcing or administering the proposed rule and therefore, a local employment impact statement is not required under Government Code, §2001.022.
PUBLIC BENEFIT
Duane Milligan, P.E. has determined, as required by Government Code, §2001.024(a)(5), that for each year of the first five years in which the proposed rule is in effect, the public benefit anticipated as a result of enforcing or administering the rule will be increased clarity by removing a procedure that is no longer used.
COSTS ON REGULATED PERSONS
Duane Milligan has also determined, as required by Government Code, §2001.024(a)(5), that for each year of that period there are no anticipated economic costs for persons, including a state agency, special district, or local government, required to comply with the proposed rule and therefore, Government Code, §2001.0045, does not apply to this rulemaking
ECONOMIC IMPACT STATEMENT AND REGULATORY FLEXIBILITY ANALYSIS
Duane Milligan has also determined, as required by Government Code, §2001.024(a)(5), that for each year of that period there are no anticipated economic costs for persons, including a state agency, special district, or local government, required to comply with the proposed rule and therefore, Government Code, §2001.0045, does not apply to this rulemaking.
GOVERNMENT GROWTH IMPACT STATEMENT
Duane Milligan, P.E. has considered the requirements of Government Code, §2001.0221 and anticipates that the proposed rule will have no effect on government growth. He expects that during the first five years that the rule would be in effect:
(1) it would not create or eliminate a government program;
(2) its implementation would not require the creation of new employee positions or the elimination of existing employee positions;
(3) its implementation would not require an increase or decrease in future legislative appropriations to the agency;
(4) it would not require an increase or decrease in fees paid to the agency;
(5) it would not create a new regulation;
(6) it would not expand, limit, or repeal an existing regulation;
(7) it would not increase or decrease the number of individuals subject to its applicability; and
(8) it would not positively or adversely affect this state's economy.
TAKINGS IMPACT ASSESSMENT
Duane Milligan has determined that a written takings impact assessment is not required under Government Code, §2007.043.
SUBMITTAL OF COMMENTS
Written comments on the repeal of §13.8, may be submitted to Rule Comments, General Counsel Division, Texas Department of Transportation, 125 East 11th Street, Austin, Texas 78701-2483 or to RuleComments@txdot.gov with the subject line "Testing Asphalt." The deadline for receipt of comments is 5:00 p.m. on November 11, 2024. In accordance with Transportation Code, §201.811(a)(5), a person who submits comments must disclose, in writing with the comments, whether the person does business with the department, may benefit monetarily from the proposed amendments, or is an employee of the department.
STATUTORY AUTHORITY
The repeals are proposed under Transportation Code, §201.101, which provides the Texas Transportation Commission (commission) with the authority to establish rules for the conduct of the work of the department.
CROSS REFERENCE TO STATUTES IMPLEMENTED BY THIS RULEMAKING
§13.8.Testing Asphalt.
The agency certifies that legal counsel has reviewed the proposal and found it to be within the state agency's legal authority to adopt.
Filed with the Office of the Secretary of State on September 26, 2024.
TRD-202404633
Becky Blewett
Deputy General Counsel
Texas Department of Transportation
Earliest possible date of adoption: November 10, 2024
For further information, please call: (512) 463-8630
SUBCHAPTER B. UTILITY ADJUSTMENT, RELOCATION, OR REMOVAL
The Texas Department of Transportation (department) proposes the amendments to §21.25 concerning state participation in the Relocation of Certain Publicly-Owned Utility Facilities.
EXPLANATION OF PROPOSED AMENDMENT
S.B. 2601, Texas Legislature, 88th Regular Session, 2023, amended Transportation Code, §203.092(a-4), to add water supply or sewer service corporations organized and operating under Water Code, Chapter 67, to the entities that are authorized to apply for financial assistance for the relocation of utility facilities if the relocation is required for improvements of the highway system.
Amendments to §21.25, State Participation in the Relocation of Certain Publicly-Owned Utility Facilities, add language to allow a water supply or sewer service corporation organized and operating under Water Code, Chapter 67, to qualify for the department's program for reimbursing certain costs of the relocation of utility facilities required for a state highway project.
FISCAL NOTE
Stephen Stewart, Chief Financial Officer, has determined, in accordance with Government Code, §2001.024(a)(4), that for each of the first five years in which the proposed rules are in effect, there will be no fiscal implications for state or local governments as a result of the department's or commission's enforcing or administering the proposed rules. Despite the expansion of the participants in the reimbursement program to include water supply or sewer service corporations, the fiscal year cap of $10 million dollars for this program remains in place.
LOCAL EMPLOYMENT IMPACT STATEMENT
Kyle Madsen, Director, Right of Way Division, has determined that there will be no significant impact on local economies or overall employment as a result of enforcing or administering the proposed rules and therefore, a local employment impact statement is not required under Government Code, §2001.022.
PUBLIC BENEFIT
Mr. Madsen has determined, as required by Government Code, §2001.024(a)(5), that for each year of the first five years in which the proposed rules are in effect, the public benefit anticipated as a result of enforcing or administering the rules will be to allow water supply or sewer service corporations organized and operating under Chapter 67 of the Water Code to qualify for the program and reduce the department's construction delays related to utility facilities relocation.
COSTS ON REGULATED PERSONS
Mr. Madsen has also determined, as required by Government Code, §2001.024(a)(5), that for each year of that period there are no anticipated economic costs for persons, including a state agency, special district, or local government, required to comply with the proposed rules and therefore, Government Code, §2001.0045, does not apply to this rulemaking.
ECONOMIC IMPACT STATEMENT AND REGULATORY FLEXIBILITY ANALYSIS
There will be no adverse economic effect on small businesses, micro-businesses, or rural communities, as defined by Government Code, §2006.001, and therefore, an economic impact statement and regulatory flexibility analysis are not required under Government Code, §2006.002.
GOVERNMENT GROWTH IMPACT STATEMENT
Mr. Madsen has considered the requirements of Government Code, §2001.0221 and anticipates that the proposed rules will have no effect on government growth. He expects that during the first five years that the rule would be in effect:
(1) it would not create or eliminate a government program;
(2) its implementation would not require the creation of new employee positions or the elimination of existing employee positions;
(3) its implementation would not require an increase or decrease in future legislative appropriations to the agency;
(4) it would not require an increase or decrease in fees paid to the agency;
(5) it would not create a new regulation;
(6) it would not expand, limit, or repeal an existing regulation;
(7) it would not increase or decrease the number of individuals subject to its applicability; and
(8) it would not positively or adversely affect this state's economy.
TAKINGS IMPACT ASSESSMENT
Mr. Madsen has determined that a written takings impact assessment is not required under Government Code, §2007.043.
SUBMITTAL OF COMMENTS
Written comments on the amendments to §21.25, may be submitted to Rule Comments, General Counsel Division, Texas Department of Transportation, 125 East 11th Street, Austin, Texas 78701-2483 or to RuleComments@txdot.gov with the subject line "§21.25 State Participation." The deadline for receipt of comments is 5:00 p.m. on November 11, 2024. In accordance with Transportation Code, §201.811(a)(5), a person who submits comments must disclose, in writing with the comments, whether the person does business with the department, may benefit monetarily from the proposed amendments, or is an employee of the department.
STATUTORY AUTHORITY
The amendments are proposed under Transportation Code, §201.101, which provides the Texas Transportation Commission (commission) with the authority to establish rules for the conduct of the work of the department, and more specifically, Transportation Code, §203.095, which requires the commission to adopt rules relating the relocation of utility facilities.
The authority for the proposed amendments was provided by S.B. 2601, 88th Regular Session, 2023. The primary author and the primary sponsor of that bill are Sen. Juan Hinojosa and Rep. Terry Canales, respectively.
CROSS REFERENCE TO STATUTES IMPLEMENTED BY THIS RULEMAKING
Transportation Code, §203.092.
§21.25.State Participation in the Relocation of Certain Publicly-Owned Utility Facilities.
(a) A utility that is a political subdivision,
is [or] owned or operated by a political subdivision, or is a water supply or sewer service corporation that is organized
and operating under Chapter 67, Water Code, may request that the
relocation of its utility facilities required by a state highway improvement
project be at the expense of the state under Transportation Code,
Section 203.092(a-4).
(b) To request relocation under this section, the utility must make a written request to the department and submit:
(1) documentation that the utility, because of an existing financial condition, would be unable to pay the cost of relocation in full or in part at the time of relocation or that the utility's ability to operate or provide essential services to its customers would be adversely affected by such a payment made at that time; and
(2) documentation:
(A) on the utility's ability to obtain a state infrastructure bank loan under Chapter 6 of this title (relating to State Infrastructure Bank) and its ability to obtain other financing for the relocation, including relevant financial information described in §6.23 of this title (relating to Application Procedure); or
(B) that the utility is a political subdivision, or owned or operated by a political subdivision, that has a population of less than 5,000 and is located within a county that has been included in at least five disaster declarations made by the president of the United States of America in the six-year period preceding the proposed date of the relocation; and
(3) any other information or documentation requested by the department.
(c) As soon as practicable after review and analysis of the documentation and information provided under subsection (b) of this section, the department will submit findings and recommendations to the commission for consideration.
(d) The commission will find that all or a part of the utility facility relocation is an expense of the state if:
(1) payment for all or a part of the relocation of the utility facility would not cause the department to exceed $10 million for the relocation of utilities authorized under Section 203.092(a-4) in any fiscal year; and
(2) the commission determines that:
(A) the utility is a political subdivision, [or] is owned or operated by a political subdivision, or
is a water supply or sewer service corporation that is organized and
operating under Chapter 67, Water Code;
(B) a financial condition exists, as described in subsection (b)(1) of this section; and
(C) the utility:
(i) would not be able to receive a state infrastructure bank loan under Chapter 6 of this title to finance the cost of the relocation and is otherwise unable to finance that cost; or
(ii) meets the description provided in subsection (b)(2)(B) of this section.
(e) If the commission finds that all or a part of the utility facility relocation is an expense of the state, the department and the utility shall include the terms of the department's payment of relocation expenses in an agreement concerning the relocation.
(f) Because of the fiscal constraint provided under Transportation Code, Section 203.092(e), the department:
(1) may prioritize the utility requests based on the needs of the department, including the construction schedules of the projects requiring relocation of utility facilities;
(2) may delay until the next fiscal year the payment of all or part of a claim made by a utility if at the time the claim is received by the department, the payment is prohibited by Section 203.092(e); and
(3) will not pay a claim for payment that is received by the department later than one year after the date that the relocation of the utility facility is completed.
The agency certifies that legal counsel has reviewed the proposal and found it to be within the state agency's legal authority to adopt.
Filed with the Office of the Secretary of State on September 26, 2024.
TRD-202404634
Becky Blewett
Deputy General Counsel
Texas Department of Transportation
Earliest possible date of adoption: November 10, 2024
For further information, please call: (512) 463-8630